Reducing Friction in Software Development

Reducing Friction in Software Development

Reducing Inspection Interval in Large-Scale Software Development

ÐWe have found that, when software is developed by multiple, geographically separated teams, the cost-benefit trade-offs of software inspection change. In particular, this situation can significantly lengthen the inspection interval (calendar time needed to complete an inspection). Our research goal was to find a way to reduce the inspection interval without reducing inspection effectiveness. W...

Reducing Boundary Friction Using Translation-Fragment Overlap

Many corpus-based Machine Translation (MT) systems generate a number of partial translations which are then pieced together rather than immediately producing one overall translation. While this makes them more robust to ill-formed input, they are subject to disfluencies at phrasal translation boundaries even for well-formed input. We address this “boundary friction” problem by introducing a met...

Improving Software Development Economics Part II: Reducing Software Product Complexity and Improving Software Processes

Case-Based Reasoning for Reducing Software Development Effort

How can we best find project changes that most improve project estimates? Prior solutions to this problem required the use of standard software process models that may not be relevant to some new project. Also, those prior solutions suffered from limited verification (the only way to assess the results of those studies was to run the recommendations back through the standard process models). Co...